Skip to main content link. Accesskey S
  • Help
  • HCL Logo
  • HCL Sametime wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL forums and blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
Search
Community Articles > Sametime Standard > Sametime Standard deployment scenarios > Installing Lotus Sametime 8.5.1 servers without using deployment plans
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Administrators: Previewing IBM Sametime Unified Telephony Lite Client 8.5.2 for your users

The IBM Sametime Unified Telephony Lite Client 8.5.2 Preview Guide is available for you to distribute to your users for new installations and upgrades to Lotus Sametime. This guide is designed to help your users become productive on the new software quickly, and to provide them with links to ...

Connecting to a Microsoft Office Communications Server community

Connect to a Microsoft® Office Communications Server community so that your users can exchange instant messages with Microsoft Communicator users.

Increasing the number of open files on a WebSphere Application Server SIP Proxy server running on Linux

If your IBM® WebSphere® Application Server SIP Proxy server is hosted on Linux™, increase the number of concurrent open files on the server to prevent performance problems.

Preparing the Sametime Community Server for users

Before deploying clients, set up the login and licensing requirements that suit your environment.

Summary of ports to open for Sametime Gateway

The tables below show the ports to open for external and internal firewalls to support IBM® Sametime® Gateway.
Community articleInstalling Lotus Sametime 8.5.1 servers without using deployment plans
Added by ~Zelda Chutumisonakoi | Edited by ~Denise Ekresaplopoden on July 30, 2012 | Version 172
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
If you do not have a Sametime System Console installed, it is still possible to install Lotus Sametime 8.5.1 servers. Rather than creating a deployment plan prior to installation, you can supply values when you run the installation program. You can then register the server at a later time when the Sametime System Console is available.
Tags: 8.5.1, install
The strongly recommended approach for installing Lotus Sametime 8.5.1 servers is to install a Sametime System Console first and then use the console to create a deployment plan for a given server. During installation, the server takes the installation values from the deployment plan and after installation, the new server is registered automatically with the console to become one of its managed servers. The console gives you a central administration point for all Sametime servers and offers guided activities that make installation and configuration tasks easier.

However, there are situations in which you cannot install a Sametime server in the recommended way. Such a situation may be caused by a lack of hardware for a full Sametime server installation, installation delays with the Sametime System Console, or a need for a small testing environment for a specific server. This article describes how to install a Sametime 8.5.1 server as a standalone server, which can be added later to the Sametime System Console through a separate registration utility. These instructions apply to installing a Sametime Community server, a Sametime Proxy server, a Sametime Media Manager, or a Sametime Meeting server running on AIX, Linux, Solaris, or Windows.
  • Installing a Sametime Community server without using a deployment plan
  • Installing a Sametime Proxy server without using a deployment plan
  • Installing a Sametime Media Manager without using a deployment plan
  • Installing a Sametime Meeting server without using a deployment plan

Installing a Sametime Community server without using a deployment plan

Before you begin
Install a Domino server as described in the Sametime 8.5.1 information center. Then start the Domino® server to allow validation of the Domino administrator during the installation.
If you plan to connect to a separate slide conversion server, you have configured the server and know its name and port number.
Make sure the LDAP server is running.

Installing
Follow Steps 1 - 7 from this topic in the Sametime 8.5.1 information center as you would for a regular installation: Running the community server installation program on AIX, Linux, Solaris, or Windows.

8, Click No to install without the Lotus Sametime System Console. Click Next.

9. At the Connect to Domino Server screen, provide the fully qualified host name for this Lotus Sametime Community Server. Do not use an IP address or the host's short name.

Leave 80 as the default port unless you are using another port for the HTTP server.

Enter the existing Domino administrator's user ID and password, and then click Next.

Use the common-name portion of the ID (not the hierarchical name that includes slashes). The Sametime System Console validates the administrator credentials on the Domino server.

10. At the Slide Conversion screen, do one of the following:
  • Select Use the Sametime server to host the slide conversion feature on the current server, and then click Next.
  • Select Use Sametime slide conversion server to host the slide conversion feature on a different Community Server, provide the host name and port to connect to that server, and then click Next.

11. At the LDAP screen, provide values that will be used for connecting to an LDAP server
- Provide the hostname and port of the LDAP server and click Validate. Make sure that the LDAP server is running. Once the button label changes to Validated, then click Next.

12. At the HTTP Tunneling screen, to allow Sametime clients to make HTTP-tunneled connections on port 80 to a server with a single IP address, click Enable HTTP Tunneling, and then click Next.

Selecting this feature increases the possibility that users in restrictive network environments can exchange data in chats on a Sametime Community Server that is extended to the Internet.

13. At the summary panel, review the settings, then click Install to start the installation.

14. Click Finish to close the installation screen.

15. Click Exit to close the Installation Manager.

Next steps
When you install the Lotus Sametime System Console later, register the new server to take advantage of clustering and other administrative features. For more information, see Registering a Community Server manually in the Sametime 8.5.1 information center.

Installing a Sametime Proxy server without using a deployment plan

Before you begin
Make sure that the community server is running.

Installing
Follow Steps 1 - 11 from this topic in the Sametime 8.5.1 information center as you would for a regular installation: Installing a proxy server on AIX, Linux, Solaris, or Windows.

Complete the installation by following these steps:

12. Select IBM Sametime Proxy Server as the feature to install, but do not select Use Lotus Sametime System Console to install. Click Next.

13. At the WAS Configuration screen, provide values that will be used by the WebSphere Application Server.
- Under Select the type of installation, select Standalone (Cell and Primary nodes).
- Supply the User ID and Password information and click Next.

14. At the Proxy Server Configuration screen, provide values that will be used for installing the Proxy Server.
- Enter the hostname and port of the Community Server that will be used by the Media Server and click Validate. When the button label changes to Validated, then click Next.

15. At the summary panel, review the settings, then click Install to start the installation.

16. Click Restart installation manager to close the installation screen.

17. Click Exit to close the Installation Manager.

Next steps
When you install the Lotus Sametime System Console later, register the new server to take advantage of clustering and other administrative features. For more information, see Registering a Sametime Proxy Server, Media Manager, or Meeting Server manually in the Sametime 8.5.1 information center.

Installing a Sametime Media Manager without using a deployment plan

Before you begin
Make sure the Community server is running.

Installing
Follow Steps 1 - 11 from this topic in the Sametime 8.5.1 information center as you would for a regular installation: Installing a media manager on Linux or Windows.

Complete the installation by following these steps:

12. Select IBM Sametime Media Manager as the feature to install, but do not select Use Lotus Sametime System Console to install. Click Next.

13. At the WAS Configuration screen, provide values that will be used by the WebSphere Application Server.
- Under Select the type of installation, select Standalone (Cell and Primary nodes).
- Supply the User ID and Password information and click Next.

14. At the Media Server Configuration screen, provide values that will be used for installing Media Server components.
- Provide the hostnames for Conference Manager, SIP Proxy/Registrar, and Packet Switcher
If all 3 components are to be installed on the same local system - provide the same local host name.

- Enter the hostname and port of the Community Server that will be used by the Media Server and click Validate. Make sure that the community server is running. When the button label changes to Validated, then click Next.

15. At the summary panel, review the settings, then click Install to start the installation.

16. Click Restart installation manager to close the installation screen.

17. Click Exit to close the Installation Manager.

Next steps
When you install the Lotus Sametime System Console later, register the new server to take advantage of clustering and other administrative features. For more information, see Registering a Sametime Proxy Server, Media Manager, or Meeting Server manually in the Sametime 8.5.1 information center.


Installing a Sametime Meeting server without using a deployment plan

Before you begin
You have set up the prerequisites: an LDAP server, an IBM® DB2® installation, and a meeting server database.

Make sure that the LDAP server and DB2 server are running, then follow Steps 1 - 11 from this topic in the Sametime 8.5.1 information center as you would for a regular installation: Installing a meeting server on AIX, Linux, Solaris, or Windows.

Complete the installation by following these steps:

12. Select IBM Lotus Sametime Meeting Server 8.5.1 as the feature to install, but do not select Use Lotus Sametime System Console to install. Click Next.

13. At the WAS Configuration screen, provide values that will be used by the WebSphere Application Server.
- Under Select the type of installation, select Standalone (Cell and Primary nodes).
- Supply the User ID and Password information and click Next.

14. At the Configure DB2 for the Meeting Server screen, provide values that will be used to connect to the DB2 database.
  1. Enter the fully qualified host name of the DB2 server in the Host name field.
    Do not enter an IP address or a short host name.
  2. The Port field shows the default port of 50000. Accept the default unless you specified a different port during DB2 installation or your server is using a different port.
    Linux: The default is typically 50001, but will vary based on port availability. Check the /etc/services file on the DB2 server to verify the port number being used.
  3. In the Database name, field, enter the name of the database you want to connect to.
  4. The database name is STMS unless you changed it.
    In the Application user ID field, supply the DB2 application's administrative user name that you created when you installed DB2, such as db2admin. This user has database administration authority and you will use this user ID and password whenever you work with DB2 databases for Lotus Sametime. On IBM i, this is the user profile you specified as the owner of the Meeting Server database schemas in your copy of the stms.default.response.properties file or the user profile you logged in with when you created the Gateway database schemas.
  5. In the Application password field, enter the password for the DB2 administrative user ID.
  6. Click Validate. Make sure that the DB2 server is running. Once the button label changes to Validated, then click Next.
15. At the LDAP screen, provide values for the LDAP server.
  1. (Optional) Select Configure LDAP after the installation if you prefer to configure the LDAP server manually or if your LDAP server requires an SSL connection.
  2. Enter the fully qualified domain name of the LDAP server you wish to connect to in the Host name field. Do not use an IP address or a short host name.
  3. Enter the Port of the LDAP server. The default value is 389. If your LDAP server is running on a different port, enter the correct port value here.
  4. Click Validate. Make sure that the LDAP server is running. Once the button label changes to Validated, then click Next.

16. At the summary panel, review the settings, then click Install to start the installation.

17. Click Restart installation manager to close the installation screen.

18. Click Exit to close the Installation Manager.

Next steps
When you install the Lotus Sametime System Console later, register the new server to take advantage of clustering and other administrative features. For more information, see Registering a Sametime Proxy Server, Media Manager, or Meeting Server manually in the Sametime 8.5.1 information center.

  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (102)
collapsed Versions (102)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (172)Jul 30, 2012, 3:57:08 PM~Denise Ekresaplopoden  
171Feb 2, 2011, 9:02:47 PM~Howard Preponemanikle  
170Jan 25, 2011, 9:01:34 PM~Vijay Bubfanavitchoden  
169Dec 21, 2010, 10:15:16 PM~Vijay Bubfanavitchoden  
167Dec 21, 2010, 10:15:04 PM~Vijay Bubfanavitchoden  
166Dec 21, 2010, 4:55:26 PM~Vijay Bubfanavitchoden  
165Dec 21, 2010, 4:47:32 PM~Vijay Bubfanavitchoden  
164Dec 21, 2010, 4:44:59 PM~Vijay Bubfanavitchoden  
163Dec 6, 2010, 8:47:52 PM~Vijay Bubfanavitchoden  
162Dec 6, 2010, 8:47:49 PM~Vijay Bubfanavitchoden  
161Dec 6, 2010, 8:47:46 PM~Vijay Bubfanavitchoden  
160Dec 6, 2010, 8:47:42 PM~Vijay Bubfanavitchoden  
159Dec 6, 2010, 8:45:37 PM~Vijay Bubfanavitchoden  
158Dec 6, 2010, 8:45:23 PM~Vijay Bubfanavitchoden  
157Dec 6, 2010, 8:44:58 PM~Vijay Bubfanavitchoden  
156Dec 6, 2010, 8:29:28 PM~Vijay Bubfanavitchoden  
155Dec 6, 2010, 8:28:12 PM~Vijay Bubfanavitchoden  
154Dec 6, 2010, 8:27:52 PM~Vijay Bubfanavitchoden  
153Dec 6, 2010, 8:27:29 PM~Vijay Bubfanavitchoden  
152Dec 6, 2010, 8:25:16 PM~Vijay Bubfanavitchoden  
151Dec 6, 2010, 8:13:43 PM~Vijay Bubfanavitchoden  
150Dec 6, 2010, 8:13:32 PM~Vijay Bubfanavitchoden  
149Dec 6, 2010, 8:13:05 PM~Vijay Bubfanavitchoden  
148Dec 6, 2010, 8:12:50 PM~Vijay Bubfanavitchoden  
147Dec 6, 2010, 8:12:16 PM~Vijay Bubfanavitchoden  
146Dec 6, 2010, 8:11:47 PM~Vijay Bubfanavitchoden  
145Dec 6, 2010, 8:11:36 PM~Vijay Bubfanavitchoden  
144Dec 6, 2010, 8:11:04 PM~Vijay Bubfanavitchoden  
143Dec 6, 2010, 8:10:32 PM~Vijay Bubfanavitchoden  
142Dec 6, 2010, 8:08:17 PM~Vijay Bubfanavitchoden  
141Dec 6, 2010, 8:08:07 PM~Vijay Bubfanavitchoden  
140Dec 6, 2010, 8:07:42 PM~Vijay Bubfanavitchoden  
139Dec 6, 2010, 8:07:15 PM~Vijay Bubfanavitchoden  
138Dec 6, 2010, 8:06:50 PM~Vijay Bubfanavitchoden  
137Dec 6, 2010, 8:06:46 PM~Vijay Bubfanavitchoden  
136Dec 6, 2010, 8:06:36 PM~Vijay Bubfanavitchoden  
135Dec 6, 2010, 8:05:54 PM~Vijay Bubfanavitchoden  
134Dec 6, 2010, 8:05:39 PM~Vijay Bubfanavitchoden  
133Dec 6, 2010, 8:05:31 PM~Vijay Bubfanavitchoden  
132Dec 6, 2010, 8:05:11 PM~Vijay Bubfanavitchoden  
131Dec 6, 2010, 8:04:40 PM~Vijay Bubfanavitchoden  
130Dec 6, 2010, 8:04:29 PM~Vijay Bubfanavitchoden  
129Dec 6, 2010, 8:04:21 PM~Vijay Bubfanavitchoden  
128Dec 6, 2010, 7:59:46 PM~Vijay Bubfanavitchoden  
127Dec 6, 2010, 7:51:01 PM~Vijay Bubfanavitchoden  
126Dec 6, 2010, 7:50:23 PM~Vijay Bubfanavitchoden  
125Dec 6, 2010, 7:49:39 PM~Vijay Bubfanavitchoden  
124Dec 6, 2010, 7:43:09 PM~Vijay Bubfanavitchoden  
123Dec 6, 2010, 7:42:51 PM~Vijay Bubfanavitchoden  
122Dec 6, 2010, 6:52:25 PM~Vijay Bubfanavitchoden  
121Dec 6, 2010, 6:51:56 PM~Vijay Bubfanavitchoden  
120Dec 6, 2010, 6:51:35 PM~Vijay Bubfanavitchoden  
119Dec 6, 2010, 6:51:19 PM~Vijay Bubfanavitchoden  
118Dec 6, 2010, 6:51:05 PM~Vijay Bubfanavitchoden  
117Dec 6, 2010, 6:49:44 PM~Vijay Bubfanavitchoden  
116Dec 6, 2010, 6:49:37 PM~Vijay Bubfanavitchoden  
115Dec 6, 2010, 6:49:08 PM~Vijay Bubfanavitchoden  
114Dec 6, 2010, 6:45:33 PM~Vijay Bubfanavitchoden  
113Dec 6, 2010, 6:43:45 PM~Vijay Bubfanavitchoden  
112Dec 6, 2010, 6:43:15 PM~Vijay Bubfanavitchoden  
111Dec 6, 2010, 6:43:10 PM~Vijay Bubfanavitchoden  
110Dec 6, 2010, 6:42:38 PM~Vijay Bubfanavitchoden  
109Dec 6, 2010, 6:41:27 PM~Vijay Bubfanavitchoden  
108Dec 6, 2010, 6:37:56 PM~Vijay Bubfanavitchoden  
107Dec 6, 2010, 6:37:01 PM~Vijay Bubfanavitchoden  
106Dec 6, 2010, 6:20:24 PM~Vijay Bubfanavitchoden  
105Dec 6, 2010, 6:19:11 PM~Vijay Bubfanavitchoden  Minor Change
104Dec 6, 2010, 6:16:50 PM~Vijay Bubfanavitchoden  Minor Change
103Dec 6, 2010, 6:15:31 PM~Vijay Bubfanavitchoden  Minor Change
102Dec 6, 2010, 6:15:24 PM~Vijay Bubfanavitchoden  Minor Change
101Dec 6, 2010, 6:15:19 PM~Vijay Bubfanavitchoden  Minor Change
100Dec 6, 2010, 6:15:06 PM~Vijay Bubfanavitchoden  Minor Change
99Dec 6, 2010, 6:14:51 PM~Vijay Bubfanavitchoden  Minor Change
98Dec 6, 2010, 6:14:44 PM~Vijay Bubfanavitchoden  Minor Change
97Dec 6, 2010, 6:14:29 PM~Vijay Bubfanavitchoden  Minor Change
96Dec 6, 2010, 6:13:56 PM~Vijay Bubfanavitchoden  Minor Change
95Dec 6, 2010, 6:13:36 PM~Vijay Bubfanavitchoden  Minor Change
94Dec 6, 2010, 6:12:07 PM~Vijay Bubfanavitchoden  Minor Change
93Dec 6, 2010, 6:06:23 PM~Vijay Bubfanavitchoden  Minor Change
92Nov 23, 2010, 10:58:44 PM~Vijay Bubfanavitchoden  Minor Change
91Oct 25, 2010, 6:31:25 PM~Vijay Bubfanavitchoden  
90Oct 25, 2010, 6:30:45 PM~Vijay Bubfanavitchoden  
89Oct 22, 2010, 5:55:51 PM~Vijay Bubfanavitchoden  
88Oct 22, 2010, 5:54:40 PM~Vijay Bubfanavitchoden  
87Oct 22, 2010, 5:53:09 PM~Vijay Bubfanavitchoden  
86Oct 22, 2010, 5:52:34 PM~Vijay Bubfanavitchoden  
85Oct 22, 2010, 5:52:33 PM~Vijay Bubfanavitchoden  
84Oct 13, 2010, 9:26:49 PM~Vijay Bubfanavitchoden  
83Oct 13, 2010, 9:26:20 PM~Vijay Bubfanavitchoden  
82Oct 13, 2010, 9:25:37 PM~Vijay Bubfanavitchoden  
81Oct 13, 2010, 9:25:27 PM~Vijay Bubfanavitchoden  
80Oct 13, 2010, 9:25:20 PM~Vijay Bubfanavitchoden  
79Oct 13, 2010, 9:25:01 PM~Vijay Bubfanavitchoden  
78Oct 13, 2010, 9:23:53 PM~Vijay Bubfanavitchoden  
77Oct 13, 2010, 9:23:46 PM~Vijay Bubfanavitchoden  
76Oct 13, 2010, 9:23:34 PM~Vijay Bubfanavitchoden  
75Oct 13, 2010, 9:23:20 PM~Vijay Bubfanavitchoden  
74Oct 13, 2010, 9:23:12 PM~Vijay Bubfanavitchoden  
73Oct 13, 2010, 9:21:17 PM~Vijay Bubfanavitchoden  
72Oct 13, 2010, 9:20:25 PM~Vijay Bubfanavitchoden  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software Support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility